Skip to content

Add opt-in local repair for repeated Codex onboarding - #16

Open
priva7eer wants to merge 2 commits into
Netroforge:mainfrom
priva7eer:fix/local-onboarding-repair
Open

priva7eer wants to merge 2 commits into
Netroforge:mainfrom
priva7eer:fix/local-onboarding-repair

Conversation

@priva7eer

Copy link
Copy Markdown

The official Codex welcome screen can reappear despite saved completion flags: its onboarding decision treats failed or paused state reads as first use. This adds an explicitly invoked developer repair for openai.chatgpt version 26.1007.21434 that waits for a successful read and exits an already open welcome page when completion is confirmed.

The script validates the supported version and expected code, saves backups, supports rollback and is excluded from the Extras VSIX. It never runs automatically and does not change Extras runtime behavior. Documentation covers application, verification, rollback and the limitation that a failed read waits for a successful refetch.

Validation:

  • npm test: 18/18 passing on current upstream main plus this change; four focused tests reproduce the original decision and check repaired behavior, first use, automatic exit, validation, backups, idempotence and restore.
  • npm run package: passed; confirmed the repair script and tests are excluded from the VSIX.
  • The reporter confirmed the repeated welcome screen stopped appearing after local installation and reloading VS Code. The precise request failure that triggered it remains unverified.

This PR offers an optional local troubleshooting tool for an upstream OpenAI extension defect; it does not claim the defect originates in Codex Extras.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant